Repository navigation
Move Tell toward typed Go runtime and native GPUI Studio - #15
Merged
Merged
Conversation
Collaborator
|
Thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This begins the migration proposed by Bhuvan: make the native Go implementation the primary runtime, introduce typed Tell syntax, deprecate the Python runtime/IDE, and start the Rust GPUI editor.
1. LLVM workflow cost
2. Typed Go dialect
let number result be 42.to factorial(number: n) out number:.--typedvalidation for run, check, and build.3. Python/Tk deprecation
tell-ideentry point from new Python package installations.python -m tell idetemporarily available with a deprecation warning.4. Rust/GPUI Studio
studio/.Compatibility and performance status
This is a staged migration. Python is not deleted, and the typed dialect is opt-in. The Go runtime still uses the existing dynamic value representation; this PR adds typed validation and carries function contracts into bytecode, but does not yet claim faster execution or compilation. Type-directed bytecode specialization and performance benchmarking are a follow-up phase.
The new GPUI app is an initial editor foundation rather than a complete Zed replacement. Memory and CPU improvements need measurement.
Validation
The native Go tests/race detector/vet, Python compatibility tests, and combined test/build workflow have passed. Linux and Windows validation have passed. The macOS runtime-package job is still queued at the last check. Full LLVM and GPUI toolchain builds are available through their scheduled/manual workflows.